Use Mapbox API v4 #9
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
runetvilum
added a commit
to runetvilum/Leaflet.MakiMarkers
that referenced
this pull request
Jun 5, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The previously used v3 API is deprecated. This switches Leaflet.MakiMarkers to use the newer v4 API. Unfortunately v4 requires a valid Mapbox API token with every request. Version 2.0.0 of Leaflet.MakiMarkers allows the developer to specify an accessToken via
L.MakiMarkers.accessTokenor with each icon as part of the config object in theL.MakiMarkers.icon(confg)constructor.